> Another possibility, one I hope to do with my gamekit:
>
> Provide a directory in either ~/Library or
> /LocalLibrary called, say, "MiscKit" which contains
> any "extras", perhaps in subdirectories if you like.
> Then, a developer using the kit can either provide their
> own custom version inside the app wrapper (to override)
> or use the standard .nib. One advantage of this is that you
> only need to keep one copy in a given filesystem...
>
I would have to say that this is asking for trouble. In my opinion an app should be as self-contained as possible. For development having some common nibs in LocalLibrary might be OK, but for an end-user, it's only one more thing to go wrong, one more thing to inadvertantly delete. Nib files aren't that big anyway.
